Are you removing, renaming or moving a folder in this PR?

• No, I'm not changing any folders (skip to TeamSites and delete the rest of this section)
• Yes, I'm removing, renaming or moving a folder

⚠️ TeamSites ⚠️

Examples of a TeamSite: https://va.gov/health and https://benefits.va.gov/benefits/. This scenario is also referred to as the "injected" header and footer. You can reach out in the #sitewide-public-websites Slack channel for questions.

Did you change site-wide styles, platform utilities or other infrastructure?

• No
• Yes, and I used the proxy-rewrite steps to test the injected header scenario

Summary

• This PR adds links to the facility website to the appointment details pages
• Appointments (VAOS) Team
• This is not behind a Flipper

Related issue(s)

• Add the link to the Facility Name on the Appointment Details Page va.gov-team#89129

Testing done

• Tested locally
• Updated unit tests to test for the new links

Screenshots

Note that the full matrix of all changed pages will need 2 (before, after) * (6 (VA appointment modes) * 3(upcoming confirmed, upcoming cancelled, past) + 1 (VA request) * 2 (pending, pending cancelled)) = 40 screenshots which is probably too many. Instead I'll sample a subset of the full matrix of changed pages.

	Before	After
VA Request - Pending
VA Request - Pending cancelled
Video ATLAS - Upcoming
Video VA - Upcoming cancelled
Claims - Past
In Person - Upcoming
Phone - Upcoming cancelled
Video - Past

What areas of the site does it impact?

Appointments (VAOS)

Acceptance criteria

Quality Assurance & Testing

• I fixed|updated|added unit tests and integration tests for each feature (if applicable).
• No sensitive information (i.e. PII/credentials/internal URLs/etc.) is captured in logging, hardcoded, or specs
• Linting warnings have been addressed
• Documentation has been updated (link to documentation *if necessary)
• Screenshot of the developed feature is added
• Accessibility testing has been performed

Error Handling

• Browser console contains no warnings or errors.
• Events are being sent to the appropriate logging solution
• Feature/bug has a monitor built into Datadog or Grafana (if applicable)

Authentication

• Did you login to a local build and verify all authenticated routes work as expected with a test user